PR Summary

This PR updates several GitHub Actions workflows and documentation to improve the deployment process for documentation and integrate release-notes management. The main changes include:

• In the deploy-docs-staging workflow, a dynamic run-name has been added to better identify runs using either the workflow run ID or commit SHA.
• The merge-main-into-staging workflow now includes a dynamic run-name and supports an additional trigger via the repository_dispatch event with type release-notes-published. This allows external dispatches (from a release-notes repository, for instance) to trigger the merge process.
• Minor formatting adjustments in the workflow file regarding environment variable configuration for clarity.
• Updates to the AGENTS.md documentation clarify that release-note content is sourced from a separate repository (validmind/release-notes). Instead of generating a documentation pull request, a dispatch event triggers the existing merge workflow which is responsible for staging deployment. This clarification helps explain the modified flow for handling release notes and documentation promotion.

Test Suggestions

• Trigger the deploy-docs-staging workflow manually (or simulate a push) to verify that the run-name is properly assigned and reflects the expected dynamic value.
• Dispatch a repository_dispatch event with the type 'release-notes-published' to ensure that the merge-main-into-staging workflow is activated correctly.
• Verify that the merge workflow deletes the temporary branch as expected when the job completes successfully.
• Check the updated documentation in AGENTS.md to ensure that it accurately reflects the new release-notes triggered deployment process.

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

Lighthouse check results

✓ INFO: No site pages to audit in this PR.

Commit SHA: a9b37e1